dns resolution
We are using a windows 2003 server and have DNS active. We seem to have a dns problem which affects a few workstations on the network.
1 Workstation cannot access our own domain name.
When we enter the IP address rather than the actual domain name, it is resolved to our router!
ie we enter our domain name www.ourdomainname.co.uk and we get the router interface, also when we enter the IP address we get the same thing.
On our server, we can access the website by entering the domain name ie www.ourdomainname.co.uk, but entering the ip address brings up our router again!
On other workstations, they can access the web site by entering the domain name, but the IP address brings up our router.
We have also just implemented DHCP on our server. The router was providing this service previously.
Any help would be much appreciated
1 Workstation cannot access our own domain name.
When we enter the IP address rather than the actual domain name, it is resolved to our router!
ie we enter our domain name www.ourdomainname.co.uk and we get the router interface, also when we enter the IP address we get the same thing.
On our server, we can access the website by entering the domain name ie www.ourdomainname.co.uk, but entering the ip address brings up our router again!
On other workstations, they can access the web site by entering the domain name, but the IP address brings up our router.
We have also just implemented DHCP on our server. The router was providing this service previously.
Any help would be much appreciated
I would also mention that if there are entries in the DHCP portion of a computers TCP, they over ride DHCP, so it is important to make sure the setting are all empty.
compare
ipconfig /all
for a workig and nonworking computer.
Also make sure that DHCP and DNS setting s are correct.
See the MS site for best practice guidelines.
I hope this helps !
compare
ipconfig /all
for a workig and nonworking computer.
Also make sure that DHCP and DNS setting s are correct.
See the MS site for best practice guidelines.
I hope this helps !
ASKER
I can confirm that the settings on the network card IP properties for our server are set to the local server IP address.
We have a forwarder set to external ISP DNS addresses.
When running ipconfig all of the settings seem to be correct, ie the dns server is the server local IP address. the default gateway is set to the router IP address.
I have added a new host record for www.ourdomainname.co.uk pointing to our website IP aadress. Have flushed the cache.
Still the same.
When I run nslookup www.ourdomainname.com we get an initial error :-
can't find server name for address 192.168.2.182 (our server IP address)
None existent domain.
Server Unknown
Name : www.smartcomputers.co.uk.sheffield.smartcomputers.co.uk
Address :- 83.223.116.192
now the last resolution looks wrong to me. But what have I done wrong?
We have a forwarder set to external ISP DNS addresses.
When running ipconfig all of the settings seem to be correct, ie the dns server is the server local IP address. the default gateway is set to the router IP address.
I have added a new host record for www.ourdomainname.co.uk pointing to our website IP aadress. Have flushed the cache.
Still the same.
When I run nslookup www.ourdomainname.com we get an initial error :-
can't find server name for address 192.168.2.182 (our server IP address)
None existent domain.
Server Unknown
Name : www.smartcomputers.co.uk.sheffield.smartcomputers.co.uk
Address :- 83.223.116.192
now the last resolution looks wrong to me. But what have I done wrong?
ASKER
I have noticed that our local dns name is location.ourdomainname.co.
We were told that we could call our local name whatever we liked, but is it this which is causing our problems?
We were told that we could call our local name whatever we liked, but is it this which is causing our problems?
ASKER
sorry that should read "as recommended, for www.ourdomainname.co.uk"
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Aso use
dnsstuff.com and http://dnsreport.com to check that you have set up your public DNS correctly.
I hope this helps !
dnsstuff.com and http://dnsreport.com to check that you have set up your public DNS correctly.
I hope this helps !
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for your help here. We tried all of the things suggested without success, but we eventually found out that our web site host had got problems with his name server!! Your suggestions, whilst not resolving the problem directly, enabled us to track down the source of the problem. I will therefore split the points.
Once again, many thanks.
Once again, many thanks.
on your server run NSLOOKUP www.ourdomainname.co.uk and take note of what IP it resolves to. Since that is the 'correct' IP that machines in your network can get to your website at then you need to make sure that on your internal DNS server (or whatever DNS server your clients are pointed to) that there is an A record for www.ourdomainname.co.uk that points to this same IP.
before you test make sure to run ipconfig /flushdns on the client machine to clear the DNS cache. If not you will be looking at the old incorrect cached DNS records and not looking at the correct ones.