18 replies
by dlester Accepted solution
by alfa11 Accepted solution
The company sites browsing issue happens because the local domain is named the same way as the public domain, so when you try to access the site it tries to resolve its name with the internal DNS database. As I suppose this sites are being hosted outside your office you have to add this sites as A host in the DNS Servers pointing to the sites public IP.
Regarding the other issue it would be better that you tell us how the DNS and the DHCP are configured.
Regards
by curlergirl Accepted solution
I may be misinterpreting, but from the way your question is phrased, it sounds like your server is set to use DHCP to obtain its IP address information. A server should NEVER be set up to use DHCP. Set the server's IP address information manually.
As for the web site addresses, if your private and public domains are the same, this is why you're having that problem. You can add these addresses manually to your DNS zone. For example, if the external host is called "www.mydomain.com," add a DNS Host (A) record for "www" and enter the external (public) IP address of that server.
by dlester Accepted solution
by alfa11 Accepted solution
by sgt_shultz Accepted solution
Did you have a look in the Server to see that the server is allowing dns updates from all clients. there are a couple of settings in there, sounds like you have yours 'secured' and it is not allowing dns updates from the clients. I'll have to go and find you the mskb article but maybe have a look, i believe it is on the security tab of the properties of the dns server.
Let us know what os versions your workstations are running (and the sp level). then we can snap better as to what is happening
BTW, Is this SBS by any chance?
RE: your difficulty with certain websites. Are you saying that you have a forwarder properly configured (you have removed * from the root hints and configured a forwarder for addresses outside your LAN to your ISP's dns server?)
If yes, then I would try adding the troublesome sites to the 'trusted' zone on the Server. if no joy a tracert might be interesting. is there nothing in the event log on the server
by dlester Accepted solution
by curlergirl Accepted solution
by dlester Accepted solution
Ok, i wanted to let everyone see the config as it is to help troubleshoot this, follow the link to my flickr account and take a look, i included the nslookup as well for you to see the error i get. And i took out my ISP name servers from the root hints, thank you for pointing that out.
Flickr Link:
http://www.flickr.com/photos/agentbristow/sets/72157601763346286/show/
by cg it Accepted solution
take out the wildcard. [ * ] in the forwarders. Just have all other DNS domains for forwarders.
so what are your namespace zones for your domain names? and is there a forward lookup zone for each namespace? in the forward lookup zone what resource records do you have? Only contigious namespaces can span the same zone e.g. ..local
if you have different namespaces you need different DNS zones.
minimum, you need an SOA and A records which says ..local = 192.168.110.7 for each domain your hosting DNS
and that is only for internal clients.
further, if you use DHCP, check your options for DNS [think is option 15] clients obtain DNS information from DHCP via options. If your DHCP DNS options aren't giving clients proper information NSlookup will fail.
see MS KB article # 187800
by dlester Accepted solution
by curlergirl Accepted solution
Derek, as someone else already posted, you need to remove the "*" from your DNS forwarders tab. If you are going to set up forwarders at all, they should be set up under the "All other DNS domains." So, delete the "*", then click on All other DNS domains and then add your forwarders there.
That said, you don't actually need forwarders at all if your root hints are configured (which they are by default). I would say for now just delete all of the forwarders and see if you still have the same problems.
by cg it Accepted solution
for your DNS server named ceefs1= 192.168.110.7
that is for the domain classicequine. the SOA record should also show this.
all the other host records appear to be client computers.
queries for hosts for the DNS zone classicequine.local will be resolved by this DNS server. All other queries won't be resolved by this DNS server and be forwarded to other DNS servers for resolution[internet name servers] [unless you have other zones for other domains].
if you need this DNS server to answer queries for other domains, then you need forward lookup zones for those domain names.
You didn't expand dnsdomains so it's hard to tell if your hosting other domains not within the classicequine.local namespace.
your initial question indicates you have multiple DNS zones which are not in the contigious namespace classicequine.local.
is this true?
by dlester Accepted solution
by cg it Accepted solution
use AD intergrated updates for DNS and I believe it was St. Shultz who said to force clients to update DNS. you can also change the default TTL in DHCP to something longer than 7 days [after which 3 days clients will contact DHCP for renewals].
Typically, DHCP remembers clients and gives out the same address to the same client, even after a forced release/renew.
make sure ALL your options in DHCP are configured correctly.
Web pages won't load using the FQDM on the LAN can be a couple of things. First your local network DNS server doesn't forward requests to internet name servers for resolution so the user gets the error 403 page can not be displayed.
Firewall might filter outbound traffic to drop packets that are destined for a local server if your web server is on the local network. You can fix this problem by removing the web server from the local network and using a DMZ port behind the perimeter firewall but before the local network and mapping port 80 to go to the web server address. This will not interfer with user outbound traffic requests for web pages. Also if your DNS server is authoritative for your public web sites, you might consider changing that configuration. Add a DNS server that is authoritative for your public domain names that is NOT on the local network and only resolved your public domain names to your public IP address.
IIS on the web server isn't configured properly using all unassigned addresses and host headers.
by dlester Accepted solution
by cg it Accepted solution
your DNS should forward all queries not resolved locally. If that is setup properly, then requests for http://www..com will be resolved by the hosting companies DNS.
if your internal network has the same FQDN as your external hosting company, then your DNS will resolve the name and will try to send the request to a web server. because there's no web server on the lan to provide a web page, users get a page can not be displayed.
here's a link on W2003 Server conditional forwarders.
by mrepuski Accepted solution
DNS is not difficult to configure but has be correct to work properly.
What is DNS used for? Very simply it changes host names (FQDN - Fully qualified domain name) to IP addresses.
When DNS is combine with an Active directory domain dns also provides references to domain service records that then point to the
FQDN of the server (normally a DC) and then finally resolves to an IP.
DNS is services should either know all or nothing about answers for any given request for a domain.
When your create an active directory domain the domain name is a private domain name space that only your dns server(s) will know.
If any system that belongs to your domain point to other DNS server either along with your DNS server(s) or just to the public DNS
server(s) you will have user logon and resource location issue. The issues will present themselves as either slow response or resolution failures.
From the posts your domain name is "classicequine.local" which is fine. It appears from the DNS records that you have one DC (Domain
Controller) at 192.168.0.7. You also have another server at 192.168.0.8. I hope this other server is not a DC as records relating to this server as a DC are not present.
I see two SOA (start of authority) servers. This is an odd thing to see unless they are both DC's and run the DNS service.
For DNS using normal flat file base DNS there can only be on SOA server. When running AD and using integrated DNS any DC running DNS
can be a SOA. (This is a feature of integrated zones as the data is held in the AD database).
I also can see a delegated subdomain called web, I am no sure what this is for. If not needed remove it.
This subdomain create a name space "web.classicequine.local"
Keep in mind that a domain name does not include a host name.
Your domain "classicequine.local" has a DC called ceefs1. The FQDN is ceefs1.classicequine.local
Ok. so this is the best course of action.
1) Fix the DNS service on the DC (First DC if there are more than 1)
2) Fix the DNS settings on the DC's NIC and test browsing. (Be careful browsing on a DC)
3) Fix the DNS settings on any servers NIC and test browsing
4) Fix the DHCP service so that it offers the correct IP's for gateway, DNS, WINS, node type
5) Refresh the IP on a DHCP client and test
1) Fixing the DNS service on the DC
* Check the zone types and ensure that Dynamic update is set to Secure and non secure.
This option will allow all types of clients to update DNS records.
This should help with records not updating for clients.
Secure only updates requires domain membership and the correct permissions to update records
No, prevents dynamic updates and will require the admin (you) to update records, Very boring.
* ensure that the forwarders are correct and working. The DNS properties sheet that you opened to updated the forwarders also has a
tab to test dns functionality. The monitoring tab. Simple tests local requests and recursive tests public names.
If your recursive tests will not pass either the forwarders have and issue or your firewall / gateway is blocking DNS.
If the gateway blocks DNS it may be acting as a DNS proxy. IF this is the case the gateway needs to hold the forwards and your DNS
server should forward to the gateway.
2) Fixing the DNS settings on the DC
* Once the DNS Server Service is working correctly then confirm that the DC is pointing to itself for DNS on its network card.
Note: A dc should have only 1 NIC and 1 IP and it must be statistically assigned IP.
If you have another DC or internal DNS server this can be added as a the secondary DNS IP
* flush and register the DNS settings for the DC or reboot the server.
to manually register the DNS settings enter the follow command at the command prompt
ipconfig /flushdns
net stop netlogon
net start netlogon
ipconfig /registerdns
* wait a few minutes and then test dns by pinging the DC by host name and FQDN.
If this works try browsing to the pages in question if it failed try below
If you are having issues try loading the support tools and run the following1
netdiag /v /l /fix
test again
3) Fix DNS on all other Servers
All that needs to be done here if the above is working is to ensure that the network cards only point to the internal DNS server.
(In this case the DC's IP), flush the dns cache and test. If it fails it is not the servers fault. If the IP fails to bring up
the web page it is a networking / firewall issue.
4) Fix DHCP
Check the scope options for the DHCP Server, confirm the gateway, DNS sever, and WINS if in use. The DNS IP offered must be the DC
only. (you can include any other local internal DNS servers if working correctly). One thing to ensure is hat only 1 DHCP server is
running on the subnet. If the gateway is your DHCP server ensure that you can change scope options. IF not more the DHCP to a Server.
5) Fix DHCP Client's
Check the NIC settings for the client. Both IP and DNS should be auto detect. If ok at a command prompt renew the IP address.
ipconfig /release
ipconfig /renew
Once the client has a new IP check all the IP settings by running the following
ipconfig /all
DNS should now point to internal DNS servers only
test dns by pinging the DC's host name and them the FQDN,
if the ping works browse the web to a known page then try the trouble page
Again try using the web pages IP. If this fails then there may be network issue other than DNS at hand
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending