Re: SBS 2008: nslookup Default Server: Unknown

On Wed, 19 May 2010 20:24:53 -0500, andman-8
<andman-> wrote:

>
>I'm trying to configure a new install SBS 2008 server and I am running
>into problems the MX record and DNS.
>
>I attached screenshot from nslookup:
>Default Server: Unknown
>Address: fe80:5237:53b0:ef5:1787
>
>Also attached screenshots from ipconfig/all (I will start typing, but
>the thread is long):
>Windows IP Configuration
>
>Host Name...................: GRR-SERVER
>Primary Dns Suffix.........: grr-local.local
>Node Type...................: Hybrid
>IP Routing Enabled........: No
>WINS Proxy Enabled......: No
>DNS Suffix Search List...: grr-local.local
>example.com
>test1.example.com
>etc...please see screenshot attached.
>
>What do I do?
>
>Thanks,
>
>Andy
>
>
>+-------------------------------------------------------------------+
>|Filename: ipconfig all 2.jpg |
>|Download: http://forums.techarena.in/attachmen...hmentid=10939|
>+-------------------------------------------------------------------+


What exactly are you having problems with regarding the MX record?

FYI, the MX record is not something created internally. The MX record
is created on your public zone, wherever your public zone name is
being hosted. The MX record tells the world that your server is
authoriative to receive mail for your public domain name.

When creating an MX record, with using SBS2008, it setups a record to
be referred to externally. By default it would be
"remote.YourExternalDomainName.com." or ".net", etc. Then you would
create a record called "remote" under your external domain name at
your DNS hosting company's control panel or configuration page, and
provide the external IP of your firewall. Then you create an MX
record, leave the hostname blank, and point it to
remote.YourExternalDomainName.com.

Internally, an MX record is not used. Mail is routed internally within
Exchange between users, and does not use an MX record.

Ace

This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.

On Sat, 22 May 2010 01:10:19 -0400, "Ace Fekay [MVP - Directory
Services, MCT]" <> wrote:

>On Wed, 19 May 2010 20:24:53 -0500, andman-8
><andman-> wrote:
>
>>
>>I'm trying to configure a new install SBS 2008 server and I am running
>>into problems the MX record and DNS.
>>
>>I attached screenshot from nslookup:
>>Default Server: Unknown
>>Address: fe80:5237:53b0:ef5:1787
>>
>>Also attached screenshots from ipconfig/all (I will start typing, but
>>the thread is long):
>>Windows IP Configuration
>>
>>Host Name...................: GRR-SERVER
>>Primary Dns Suffix.........: grr-local.local
>>Node Type...................: Hybrid
>>IP Routing Enabled........: No
>>WINS Proxy Enabled......: No
>>DNS Suffix Search List...: grr-local.local
>>example.com
>>test1.example.com
>>etc...please see screenshot attached.
>>
>>What do I do?
>>
>>Thanks,
>>
>>Andy
>>
>>
>>+-------------------------------------------------------------------+
>>|Filename: ipconfig all 2.jpg |
>>|Download: http://forums.techarena.in/attachmen...hmentid=10939|
>>+-------------------------------------------------------------------+
>
>
>What exactly are you having problems with regarding the MX record?
>
>FYI, the MX record is not something created internally. The MX record
>is created on your public zone, wherever your public zone name is
>being hosted. The MX record tells the world that your server is
>authoriative to receive mail for your public domain name.
>
>When creating an MX record, with using SBS2008, it setups a record to
>be referred to externally. By default it would be
>"remote.YourExternalDomainName.com." or ".net", etc. Then you would
>create a record called "remote" under your external domain name at
>your DNS hosting company's control panel or configuration page, and
>provide the external IP of your firewall. Then you create an MX
>record, leave the hostname blank, and point it to
>remote.YourExternalDomainName.com.
>
>Internally, an MX record is not used. Mail is routed internally within
>Exchange between users, and does not use an MX record.
>
>Ace
>
>This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.
>
>Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.
>
>Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
>Microsoft Certified Trainer
>Microsoft MVP - Directory Services
>
>If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.


I forgot to mention, the nslookup message "Default Server: Unknown" is
due to not having a reverse zone created for your subnets, or the PTR
record for the DNS server is missing. When nslookup initializes, it
simply grabs the IP address of the DNS server it will use during its
session, and tries to pull the name of the server from the reverse
zone. If the zone is missing, or a PTR entry doesn't exist for the DNS
server, you will see that message. It's not an error, just a message.

I see it is defaulting to the IPv6 address. DO you have a reverse zone
for IPv6, or for 192.168.1.0?

Ace