Computing.Net > Forums > Windows Server 2003 > DNS not resolving Domain.local

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Click here to start participating now! Also, check out the New User Guide.

DNS not resolving Domain.local

Reply to Message Icon

Name: GavinR
Date: April 17, 2009 at 15:13:19 Pacific
OS: Windows Vista
Product: Hewlett-packard / Ml115
Subcategory: Configurations
Comment:

Evening,

Hopefully this should be an easy answer for someone out there.

Im having a DNS issue. Somewhere along the lines i have not configured DNS settings correctly.

I only spotted this recently when i had a problem with GPO's not applying, whilst my second DC was down. I have tracked the fault back to the client machine not being able to access the SYSVOL folder on DC1 using the domain.local name. \\domain.local\sysvol


When i perform a NSLOOKUP on DOMAIN.LOCAL it only resolves the Second DC and not the first.

I need to get DNS to resolve both DC's IP addresses again.

Do i need to add a record manually?

Any help would be appreciated.

Gavin



Sponsored Link
Ads by Google

Response Number 1
Name: guapo
Date: April 19, 2009 at 05:34:45 Pacific
Reply:

Add it to the hosts file.

Example:
192.168.0.100 domain.local

How do you know when a politician is lying? His mouth is moving.


0

Response Number 2
Name: GavinR
Date: April 19, 2009 at 09:21:17 Pacific
Reply:

I agree that would work, however that is more of a work around than a fix.

Plus i would have to make sure i add a line to the host file for each of the DC's otherwise any requests would always be sent to only one DC. Meaning no fault tollerance.

Maybe i'll have to demote it, and then re-dcpromo it so it recreates the missing dns record.


0

Response Number 3
Name: scurlaruntings
Date: April 19, 2009 at 11:47:18 Pacific
Reply:

DNS records can be manually/dynamically added to DNS. Thats the whole purpose of DNS instead of using host files. Assuming the server is also a GC and Domain controller then its records should already exist in DNS. Have you configured your DHCP scope to hand out the primary and secondary DNS? Can this other DNS server be pinged via IP address? If so have a look at its DNS and ensure it can do recursive and iterative queries. The DNS console will allow you to check if the said DNS server is capable of name resolution.


0

Response Number 4
Name: guapo
Date: April 19, 2009 at 14:14:52 Pacific
Reply:

I think you would be asking for trouble if you start playing with dcpromo for a something like that.

How do you know when a politician is lying? His mouth is moving.


0

Response Number 5
Name: GavinR
Date: April 19, 2009 at 15:06:27 Pacific
Reply:

Both servers are GC's.

The clients are configured with both servers IP's for DNS resolution.

Both DNS servers can correctly resolve internal and external ip adresses.

My problem is that they seem to have missing records.
NSLOOKUP DOMAIN.LOCAL will only resolve DC2. If i am correct it should give the ip address of all DC's within the domain.

Here's an example of what i mean.(Same results regardless of DNS server used)

NSLOOKUP DC1
192.168.1.200

NSLOOKUP DC2
192.169.1.201

NSLOOKUP DOMAIN.LOCAL
192.168.1.201

Where in the DNS can i manually add the record.


0

Related Posts

See More



Response Number 6
Name: guapo
Date: April 19, 2009 at 19:55:41 Pacific
Reply:

http://technet.microsoft.com/en-us/...

See if any of the nslookup options do anything for you.

How do you know when a politician is lying? His mouth is moving.


0
Reply to Message Icon

FSMO Roles and GC Vpn problem



Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows Server 2003 Forum Home


Sponsored links

Ads by Google


Results for: DNS not resolving Domain.local

2003 server - zone not resolving www.computing.net/answers/windows-2003/2003-server-zone-not-resolving/6033.html

DNS, Fully Qualified Domain, TLD www.computing.net/answers/windows-2003/dns-fully-qualified-domain-tld/3047.html

Domain Local Groups www.computing.net/answers/windows-2003/domain-local-groups/5408.html