IIS 5.0 /Exchange Server 2000/W2K Server/DNS

try giving each site a host header name.

M

From cmd, on PC4 try nslookup www.yoursite.dk and then try nslookup www.yoursite.dk ns.get2net.dk

do you get the same IP?

if you are a get2net costumer then try ns.dis.dk instead.

Host header names are in use.
My ISP provider is WorldOnline as indicated below.

Cut\'n\'paste of suggested procedure follow (note that external IP address and domain names has been changed):

==============================
C:\\>nslookup www.domain2.dk
*** Can\'t find server name for address 192.168.1.1: Non-existent domain
Server:  ns000.worldonline.dk
Address:  212.54.64.170

Name:    maindomain.dk
Address:  XXX.XXX.XXX.XXX
Aliases:  www.domain2.dk.maindomain.dk


C:\\>nslookup www.domain2.dk ns.get2net.dk
Server:  ns.get2net.dk
Address:  195.82.195.101

Non-authoritative answer:
Name:    maindomain.dk
Address:  XXX.XXX.XXX.XXX
Aliases:  www.domain2.dk.maindomain.dk

C:\\>
===============================


Is this suggesting that I have a problem with my DNS setup?
The above printout differs from a similar one of the functioning PC\'s only by adding the: \"Non-authoritative answer:\" line to the nslookup request.

du siger du har åbnet port 80, hvad med port 53 der bliver brugt af dns\'en??

Den er lukket! Jeg er inde bag routeren og det virker jo udefra så hvorfor skal den være åben?

I ts always easyer to help on site, harder through typing so I need to know more.
Can you publish here the resluts of an ipconfig /all?
which OS do you have on PC 4?

C:\\>ipconfig /all

Windows 2000 IP Configuration

        Host Name . . . . . . . . . . . . : venus
        Primary DNS Suffix  . . . . . . . : maindomain.dk
        Node Type . . . . . . . . . . . . : Broadcast
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : maindomain.dk

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Intel(R) PRO/100B PCI Adapter (TX)
        Physical Address. . . . . . . . . : 00-A0-C9-4C-F9-21
        DHCP Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.1.13
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.2
        DNS Servers . . . . . . . . . . . : 192.168.1.1
                                            212.54.64.170
                                            212.54.64.171

All PC\'s is running Window 2000

here we go. shouldn\'t your gate way be 192.168.1.1 ? DNS server is the 212 IP\'s

it\'s as if you ask your router to resolve names

My router is on address 192.168.1.2 and the W2K/Exchange/DNS server on 192.168.1.1

The two 212. addresses is WorldOnline DNS servers (same addresses supplied to the DNS server itself), and they are included on the workstations only to ensure that the internet connection will work from here even if tne local DNS server is down.

I see. but your nslookup shows as if there is no DNS server configured at 192.168.0.1.

can your DNS server resolve names?
also, do you run some kind of a personal fire wall on PC 4? port 53 opened is not enough. a computer requests DNS quires on port 53 but get the return on a dynamic UDP port between 1024 and 6000.

I am just trying to shoot some ideas here, your problem does seem mystical :)

M

No personal firewalls are running. Ehh... resolve names? But that is what I thought a DNS server was all about? Think I\'m about to reach the limit of my capacity in this area now.
And yes, this is really weird. I\'m actually beginning to consider reinstallig the server (the standard Microsoft way to solve a problem ;o) Logging out for tonight. Will check for suggestions tomorrow.

:) DNS server is all about that but many things can go wrong.

is your server a Domain controller? if not then you can remove the suffix from the DNS settings.

what might happen is that PC 4 looks for your IIS server host name but it tries first to find yourhostname.suffix.com and then gets an error if it can\'t resolve it with your world online DNS.

Have you tried using a host file? not that it\'s a good thing but what if we are troubleshooting for DNS when it is something else?

I will sleep on it see if I suddenly GET IT. it happens from time to time

I\'ve kept the default setting for using lmhost, but haven\'t composed a table (I\'m supposed to do that if I actually want it to work, right? Don\'t know if I want to, though. What advantages are there to be gained by doing so?)

I\'ve tried to write down the entries from the DNS panel. Please find them below:

=================================
<Forward lookup zones> (folder)
<domain1.dk> (folder)    Active Directory-integrated    Running
_msdcs (folder)
_sites (folder)
_tcp  (folder)
_udp  (folder)
(same as parent)    Start of Autority    [59],server1.domain1.dk., admin.
(same as parent)    Name Server        server1.domain1.dk.
(same as parent)    Host            192.168.1.100
(same as parent)    Host            192.168.1.1
pc1            Host            192.168.1.10
pc2            Host            192.168.1.11
server1(*)        Host            192.168.1.1
server1(*)        Host            192.168.1.100
pc4            Host            192.168.1.13

<domain2.dk> (folder)    Active Directory-integrated    Running
(same as parent)    Start of Autority    [1],server1.domain1.dk., admin.domain1.dk
(same as parent)    Name Server        server1.domain1.dk


<Forward lookup zones> (folder)
<192.168.1.x Subnet> (folder)    Active Directory-integrated    Running
(same as parent)    Start of Autority    [16],server1.domain1.dk., administrator.domain1.dk.
(same as parent)    Name Server        server1.domain1.dk
192.168.1.1        Pointer            server1.domain1.dk
192.168.1.10        Pointer            pc1.dk
192.168.1.11        Pointer            pc2.dk
192.168.1.13        Pointer            pc4.domain1.dk
=================================

pc3 has been removed from my LAN for now, and the entries in DNS deleted.
Please note: The two entries marked with an asterisk was missing ealier but still, nothing regarding the problem has changed.

If I make the following ping attempts from pc4, only the first one seems to work as the last 3 names can\'t be resolved.

ping domain1.dk        : ok
ping www.domain1.dk    : error
ping domain2.dk        : error
ping www.domain2.dk    : error

From pc1 & pc2 all 4 pings are functional, but now I\'ve discovered that the server responds exactly like pc4 when I try to connect to my homepages.

So I must conclude that my problem is server related rather than workstation specific. But why on earth pc1 & pc2 can resolve the domain names... that\'s beyond my imagination.

Note: I\'m at work right now and can only reach my server trough pcAnywhere, not any one of the workstations.

ok, You give a lot of information, that\'s good!

on your DNS server, did you define your ISP\'s DNS on the LAN properties? you should. in that way, clients will try to resolve with your DNS and once entry is not found in the database or in the cache, your DNS server will ask your ISP\'s DNS and return with an IP.

Also very important. You already told me you don\'t run any personal firewall but have you defined some sort of TCP filtering on the net card under advanced settings? it is a good thing to do, I do it to, but there are some considerations when running DNS.

Yes I\'ve done that as indicated in my comment from 06/08 2001 21:27:17.

I do not use any filtering. I\'ve deliberately keeped all possible settings on there default values (knowing I\'m not an expert in this area... yet ;o).

Since my last comment I\'ve put yet anoter entry in the <Reverse lookup zones> folder (which I by mistake wrongly called <Forward lookup zones> in my former comment):
192.168.1.100        Pointer            server1.domain1.dk

This IP addresse is the one I use to gate port 80 tcp trafic through my Cisco 677 router for web access to the IIS server (i.e. both ip address .100 and .1 is on the W2K server).

I have also added the following two zones to the forward lookup folder:

<www.domain1.dk>
<www.domain2.dk>

Now nslookup ping and browsing to all 4 host/zones is working when executed from the server.
So I\'m looking forward to try it out home on pc4 later today. I\'ll get back to you then.

Nope! It\'s the same. From pc4 it\'s not possible to browse hosted domains in Internet Explorer.

just shooting in the dark here, but have you tried another browser? could it be an application error of some sort.

Good point but Opera 5.12 can\'t show the pages either. Errormessage reads: Cannot locate remote server.

When using IE 5.5 in the attempt to reach the local site, the propertypage for the standard Microsoft error html page that shows up instead reads:
_________
General |______________________

Cannot find server
--------------------------------
Protocol: Unknown Protocol
Type: Not Available
Connection: Not Encrypted
Address: res://C:\\WINNT\\system32
(ULR)    \\shdoclc.dll/dnserror.htm#http://www.domain2.dk/

Size: Not Available
-------------------------------

Created: Not Available
Modified:  Not Available


Btw: I\'ve noticed that pc4 is slow to locate sites on the net and also when browsing other machines on the LAN as well.

Are there any unique settings on the DNS server for the various workstations attached?

I\'m totally out of ideas now.

Christ, I am beginning to dislike PC 4 :)

Have you tried removing the \"suffix\" from the DNS settings on PC 4?

Heh, I was beginning to feel the same way but I don\'t think that pc4 really is the problem.

I\'ve tried all possible combinations for suffix setting but it does not change a thing.

I have removed the dns server entry from the dns server table, and now it works. I can see my own home pages for the two domains from the darn pc4.

Any idea why?

Der er endnu ikke nogen løsning på problemet. Jeg har dog opdaget at man undertiden kortvarigt kan se de lokale domæner fra maskinen der volder problemer, men har ingen ide om hvorfor.

The slow browsing throughout the LAN could be the usual problems that occurs out of nowhere with TCP and is usually solve by installaing NetBUI (so to speak if you have under 30 hosts).

But it might just be a faulty NIC. Any chance that you could try with another? Remember to set the properties on the current card to accept DHCP so the IP-address isn\'t locked in the registry.