DNS / Nameserver Issue 1

[Murph59]

Hi,
I have an issue that I can't seem to figure out ...

I have installed DNS, Active Directory, and IIS on my Win2003 Server,
all work fine. The configurations are all pretty standard, for the
most part everything is default besides me adding a foward lookup zone
(murphy.com).

Heres my problem, I registered a domain, for example I'll say
murphy.com , and I've registered the hosts ns1.murphy.com and
ns2.murphy.com, all with Godaddy.

Now, when configuring the domain on my Win2003 server, everything
works fine (AD, IIS), except when I add my host (ns1.murphy.com) to
the list of Nameservers, it will not work. I try to access murphy.com
and it will come with a "Cannot find server error".

I can type in ns1.murphy.com into my browser and have IIS respond and
display index.htm, though ns1.murphy.com does not seem to be acting
correctly as a nameserver. I feel its a problem with my DNS but im not
sure what it could be, I have a NS entry of ns1.murphy.com listed in
my foward lookup zone.

DNS works, and resolves hostnames from the server, IIS works and if I
type the IP (or ns1.murphy.com) into a browser I can access it and AD
validated my DNS server on install and works properly.

Has anyone experienced a similar problem or have any suggestions? Help
would be greatly appreciated because I feel I have tried everything
and hit a wall.

Thanks.


P.S.
NS1.Murphy.com / Murphy.com are just example hostnames.

 

[Alshrim]

When you registered these domain names - did you add the ip address (external) to your Domain Profile at the registrar?

When you register a domain, typically, you have to add the name servers associated with that domain name to your profile - so it knows how to redirect your doman...

I know it's a mundane question, but that's the first thing that came to mind for me.

AlRo
System Administrator
Ottawa, Canada.

 

[Murph59]

Yup, NS1.Murphy.com is registered as a host and is linked to my IP....

NS1.Murphy.com is also listed as a Nameserver.

 

[theravager]

do a check on

http://www.intodns.com/

should bring up any issues.

It could be just that your new records haven't propagated to the inet nameservers. I have seen this take up to 3 or 4 days in some cases.

 

[58sniper]

A star for theravager for the link. Good stuff.

ns1.murphy.com needs to be forwarded to your DNS server, with the appropriate ports.

Pat Richard
Microsoft Exchange MVP
Contributing author The Complete Reference: Microsoft Exchange Server 2007