Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

DNS Forward Lookup Zones not always propogating


  • Please log in to reply
4 replies to this topic

#1
Tripredacus

Tripredacus

    K-Mart-ian Legend

  • Super Moderator
  • 9,921 posts
  • Joined 28-April 06
  • OS:Server 2012
  • Country: Country Flag

Donator

I've run into a behaviour I can't quite figure out. On my DNS server, I have added 1 Forward Lookup Zone with 1 A record. This A record allows clients on the network able to access a webserver on the WAN by using the FQDN. Sometimes the clients are unable to resolve the webserver address but area always able to resolve the FQDN of the DHCP/DNS server.

An Ipconfig /release /renew always fixes the problem on the client. The problem appears after first boot (or reboot) about 90% of the time. Since the regular DNS is working, but the extra lookup zone doesn't always work, I am guessing it is a configuration problem on the server... rather than a problem with the client.

What could it be?

The server runs AD, DHCP and DNS.
MSFN RULES | GimageX HTA for PE 3-5 | lol probloms
msfn2_zpsc37c7153.jpg


How to remove advertisement from MSFN

#2
allen2

allen2

    Not really Newbie

  • Member
  • PipPipPipPipPipPipPip
  • 1,814 posts
  • Joined 13-January 06
At first, I would say it might be suffix related or proxy related.
When the problem happen on the client, what is the output of "nslookup fqdn" on the client and on the server ?
Did you checked the dns server logs or tried to enable dns server logging ?

#3
Tripredacus

Tripredacus

    K-Mart-ian Legend

  • Super Moderator
  • 9,921 posts
  • Joined 28-April 06
  • OS:Server 2012
  • Country: Country Flag

Donator

UPDATE I figured out something! but I can't find why it is happening.

The DHCP/DNS server has ip x.x.x.20. After a reboot, or first boot, the DNS entry in IPCONFIG on the client is x.x.x.10. DNS does not work. After the release/renew, the DNS entry is x.x.x.20 and DNS works.

Now, x.x.x.10 is a valid system on the network... it is the hypervisor (DNS server is in the VM)... I checked the DHCP Server Scope options and both the IPv4 Server Options and the Scope Options (under the Scope tree) both have 006 option set to x.x.x.20. I can't find where the .10 ip is coming from. I've already restarted the services for DHCP and DNS.

Edited by Tripredacus, 10 September 2012 - 10:55 AM.

MSFN RULES | GimageX HTA for PE 3-5 | lol probloms
msfn2_zpsc37c7153.jpg

#4
allen2

allen2

    Not really Newbie

  • Member
  • PipPipPipPipPipPipPip
  • 1,814 posts
  • Joined 13-January 06
Then you might have 2 dhcp running on the same subnet. When you have the wrong dns, what is the dhcp server when you do an "ipconfig /all" on a client computer ?
A good test to find out the other dhcp might be stopping temporarily the dhcp server on the x.x.x.20.

#5
Tripredacus

Tripredacus

    K-Mart-ian Legend

  • Super Moderator
  • 9,921 posts
  • Joined 28-April 06
  • OS:Server 2012
  • Country: Country Flag

Donator

Then you might have 2 dhcp running on the same subnet. When you have the wrong dns, what is the dhcp server when you do an "ipconfig /all" on a client computer ?
A good test to find out the other dhcp might be stopping temporarily the dhcp server on the x.x.x.20.


You are right. The clients are getting IPs from the firewall at first, but a renew gets them from the DHCP server. Welp, time to call ops. :rolleyes:
MSFN RULES | GimageX HTA for PE 3-5 | lol probloms
msfn2_zpsc37c7153.jpg




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users