|
|
Hi,
Firstly the clients setup is:
SBS Server 2003
Windows XP clients logging into the domain
DHCP and DNS pointing to the IP of the SBS server
Gateway IP pointing to the IP of the gateway internet router.
The client is using Exchange with an additional SendAS POP3 setup that I
have setup for additional email domains (Just FYI) which requires the
following:
When a user is in the office, they need to resolve the DNS name of their
company domain to the local network IP of the SBS server,
eg. a ping mail.clientdomain.com returns a reply of 192.168.20.1 (SBS Server
IP address)
When they are outside of the office, they get a DNS resolution for
mail.clientdomain.com of the external IP address of their internet
connection, as is specified in their hosted DNS records at their ISP. (This
always works fine)
To achieve this, I have added a 'Forward Lookup Zone' into their DNS
settings on the SBS Server for 'clientdomain.com'. Into this new zone, I
have added an 'A Record' for 'mail' pointing to 192.168.20.1.
Now, on the server, a 'ping mail.clientdomain.com' returns the internal IP
address of the server - sweet!
On one of the client XP Pro PC's though, even though it has ONLY the SBS
server IP as the DNS address, it sometimes resolves to the external IP
address when on the office LAN, and seems to use an old cached DNS record of
it's own, so that it resolves mail.clientdomain.com to the external IP (This
causes the POP3 'SENDAS' setup I have to fall over). If I run an 'ipconfig
/flushdns', then try the ping again - it now replies to the (correct)
internal IP address of the server.
I created a .bat file to do the dnsflush, and added it to the 'Startup'
folder, but this seems to only work 'sometimes', as if the PC hasn't
registered DNS sometimes when it's busy starting up, so the flushdns doesn;t
take effect. - Not ideal, obviously.
On another client PC though, even a flushdns doesn't work - no matter what,
it is resolving mail.clientdomain.com to the external IP address, even
though it has one single DNS server IP (when DHCP'ing to the SBS server on
the local network), to the SBS server, and the SBS Server has the Forward
Lookup Zone seemingly working correctly.
Also, I realised that adding the zone affected other internal DNS stuff, so
I added an A record a few minutes ago for 'www', pointing to the external IP
address of their hosted website, but that doesn't seem to have worked - I
can't ping or browse to 'www.clientdomain.com' on the server - it just
errors - but am wondering if that change requires time to 'take effect' or
something.
Sorry about the long explaination, but I figure too much info is better than
not enough!
Thanks in advance
Scott
|
|
Don't worry about the www thing I mentioned - I guessed right - it was just
taking a while to 'take effect'
"UNIX" <scottnospam[ at ]calibrecomputing.com.au> wrote in message
news:uHbK6haKJHA.5448[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text] > Hi,
> Firstly the clients setup is:
> SBS Server 2003
> Windows XP clients logging into the domain
> DHCP and DNS pointing to the IP of the SBS server
> Gateway IP pointing to the IP of the gateway internet router.
>
> The client is using Exchange with an additional SendAS POP3 setup that I
> have setup for additional email domains (Just FYI) which requires the
> following:
>
> When a user is in the office, they need to resolve the DNS name of their
> company domain to the local network IP of the SBS server,
> eg. a ping mail.clientdomain.com returns a reply of 192.168.20.1 (SBS
> Server IP address)
>
> When they are outside of the office, they get a DNS resolution for
> mail.clientdomain.com of the external IP address of their internet
> connection, as is specified in their hosted DNS records at their ISP.
> (This always works fine)
>
> To achieve this, I have added a 'Forward Lookup Zone' into their DNS
> settings on the SBS Server for 'clientdomain.com'. Into this new zone, I
> have added an 'A Record' for 'mail' pointing to 192.168.20.1.
>
> Now, on the server, a 'ping mail.clientdomain.com' returns the internal IP
> address of the server - sweet!
>
> On one of the client XP Pro PC's though, even though it has ONLY the SBS
> server IP as the DNS address, it sometimes resolves to the external IP
> address when on the office LAN, and seems to use an old cached DNS record
> of it's own, so that it resolves mail.clientdomain.com to the external IP
> (This causes the POP3 'SENDAS' setup I have to fall over). If I run an
> 'ipconfig /flushdns', then try the ping again - it now replies to the
> (correct) internal IP address of the server.
>
> I created a .bat file to do the dnsflush, and added it to the 'Startup'
> folder, but this seems to only work 'sometimes', as if the PC hasn't
> registered DNS sometimes when it's busy starting up, so the flushdns
> doesn;t take effect. - Not ideal, obviously.
>
> On another client PC though, even a flushdns doesn't work - no matter
> what, it is resolving mail.clientdomain.com to the external IP address,
> even though it has one single DNS server IP (when DHCP'ing to the SBS
> server on the local network), to the SBS server, and the SBS Server has
> the Forward Lookup Zone seemingly working correctly.
>
> Also, I realised that adding the zone affected other internal DNS stuff,
> so I added an A record a few minutes ago for 'www', pointing to the
> external IP address of their hosted website, but that doesn't seem to have
> worked - I can't ping or browse to 'www.clientdomain.com' on the server -
> it just errors - but am wondering if that change requires time to 'take
> effect' or something.
>
> Sorry about the long explaination, but I figure too much info is better
> than not enough!
>
> Thanks in advance
> Scott
>
>
|
|
But I still have the problem with the DNS resolution on the clients....
"UNIX" <scottnospam[ at ]calibrecomputing.com.au> wrote in message
news:uwfja2aKJHA.3808[ at ]TK2MSFTNGP04.phx.gbl...
[Quoted Text] > Don't worry about the www thing I mentioned - I guessed right - it was
> just taking a while to 'take effect'
>
> "UNIX" <scottnospam[ at ]calibrecomputing.com.au> wrote in message
> news:uHbK6haKJHA.5448[ at ]TK2MSFTNGP05.phx.gbl...
>> Hi,
>> Firstly the clients setup is:
>> SBS Server 2003
>> Windows XP clients logging into the domain
>> DHCP and DNS pointing to the IP of the SBS server
>> Gateway IP pointing to the IP of the gateway internet router.
>>
>> The client is using Exchange with an additional SendAS POP3 setup that I
>> have setup for additional email domains (Just FYI) which requires the
>> following:
>>
>> When a user is in the office, they need to resolve the DNS name of their
>> company domain to the local network IP of the SBS server,
>> eg. a ping mail.clientdomain.com returns a reply of 192.168.20.1 (SBS
>> Server IP address)
>>
>> When they are outside of the office, they get a DNS resolution for
>> mail.clientdomain.com of the external IP address of their internet
>> connection, as is specified in their hosted DNS records at their ISP.
>> (This always works fine)
>>
>> To achieve this, I have added a 'Forward Lookup Zone' into their DNS
>> settings on the SBS Server for 'clientdomain.com'. Into this new zone, I
>> have added an 'A Record' for 'mail' pointing to 192.168.20.1.
>>
>> Now, on the server, a 'ping mail.clientdomain.com' returns the internal
>> IP address of the server - sweet!
>>
>> On one of the client XP Pro PC's though, even though it has ONLY the SBS
>> server IP as the DNS address, it sometimes resolves to the external IP
>> address when on the office LAN, and seems to use an old cached DNS record
>> of it's own, so that it resolves mail.clientdomain.com to the external IP
>> (This causes the POP3 'SENDAS' setup I have to fall over). If I run an
>> 'ipconfig /flushdns', then try the ping again - it now replies to the
>> (correct) internal IP address of the server.
>>
>> I created a .bat file to do the dnsflush, and added it to the 'Startup'
>> folder, but this seems to only work 'sometimes', as if the PC hasn't
>> registered DNS sometimes when it's busy starting up, so the flushdns
>> doesn;t take effect. - Not ideal, obviously.
>>
>> On another client PC though, even a flushdns doesn't work - no matter
>> what, it is resolving mail.clientdomain.com to the external IP address,
>> even though it has one single DNS server IP (when DHCP'ing to the SBS
>> server on the local network), to the SBS server, and the SBS Server has
>> the Forward Lookup Zone seemingly working correctly.
>>
>> Also, I realised that adding the zone affected other internal DNS stuff,
>> so I added an A record a few minutes ago for 'www', pointing to the
>> external IP address of their hosted website, but that doesn't seem to
>> have worked - I can't ping or browse to 'www.clientdomain.com' on the
>> server - it just errors - but am wondering if that change requires time
>> to 'take effect' or something.
>>
>> Sorry about the long explaination, but I figure too much info is better
>> than not enough!
>>
>> Thanks in advance
>> Scott
>>
>>
>
>
|
|
|
|
|