|
|
Hi there,
I am long time reader, first time poster on the google-goups.
I have set up a test domain named "sven.b" with AD intergrated DNS on
the DC. There are two other machines in that domain (as I said it's a
test domain). The domain is a server 2003 standard with integrated DNS
The problem is that my DNS can resolve all records EXCEPT the MX
record. Basically, the DNS Setup looks like this:
dc A 192.168.2.1
ISA A 192.168.2.2
XP A 192.168.2.10
mail MX [10] dc.sven.b
and here lies the problem. I can resolve dc.sven.b, just as I can
resolve isa.sven.b. I am testing this using ping.
I can not resolve mai.sven.b. This is where I receive no answer.
I can create a cname for dc which is
somename Alias(cname) dc.sven.b
which means that when I ping "somename.sven.b" and it get's resolved
to "dc.sven.b" . I then create a new MX record and point it to the
alias, and then I can not resolve the MX record.
I try to move the MX record to another machine (ISA.sven.b), and
again, I can not resolve it.
I have deleted the MX and the A record and recreated them again, can't
resolve.
I have flushed DNS cache, can't resolve.
I have reloaded the zone and/or restarted DNS, can't resolve.
However, if I create another DNS zone (sven.com) and I create MX
record in there, I CAN resolve it.
Basically, I can not resolve my internal MX record, whereas A and
cname records pose no problem.
Any pointers are appreciated.
|
|
svenberger1972[ at ]googlemail.com wrote:
[Quoted Text] > Hi there,
>
> I am long time reader, first time poster on the google-goups.
Note that although Google Groups is a very good way to search old posts, it
is not the best way to access the live newsgroups. For that, you should try
a newsreader client (and msnews.microsoft.com as the NNTP server). Just my
$.02
>
> I have set up a test domain named "sven.b" with AD intergrated DNS on
> the DC. There are two other machines in that domain (as I said it's a
> test domain). The domain is a server 2003 standard with integrated DNS
>
> The problem is that my DNS can resolve all records EXCEPT the MX
> record. Basically, the DNS Setup looks like this:
>
> dc A 192.168.2.1
> ISA A 192.168.2.2
> XP A 192.168.2.10
> mail MX [10] dc.sven.b
>
>
> and here lies the problem. I can resolve dc.sven.b, just as I can
> resolve isa.sven.b. I am testing this using ping.
> I can not resolve mai.sven.b. This is where I receive no answer.
>
> I can create a cname for dc which is
>
> somename Alias(cname) dc.sven.b
>
> which means that when I ping "somename.sven.b" and it get's resolved
> to "dc.sven.b" . I then create a new MX record and point it to the
> alias, and then I can not resolve the MX record.
>
> I try to move the MX record to another machine (ISA.sven.b), and
> again, I can not resolve it.
>
> I have deleted the MX and the A record and recreated them again, can't
> resolve.
>
> I have flushed DNS cache, can't resolve.
>
> I have reloaded the zone and/or restarted DNS, can't resolve.
>
> However, if I create another DNS zone (sven.com) and I create MX
> record in there, I CAN resolve it.
>
> Basically, I can not resolve my internal MX record, whereas A and
> cname records pose no problem.
>
> Any pointers are appreciated.
An MX record has to specify an A record (not an IP address, not a CNAME,
etc). You need to create an A record for mail.sven.b and then set that as
the MX record for sven.b.
|
|
[Quoted Text] > An MX record has to specify an A record (not an IP address, not a CNAME,
> etc). You need to create an A record for mail.sven.b and then set that as
> the MX record for sven.b.- Hide quoted text -
>
> - Show quoted text -
HI Lanwench,
thanks for picking up the baton.
I thought I did have an A-record in the DC (dc A
192.168.2.1 ) and used that to have the MX record pointed to (mail
MX [10] dc.sven.b). The cname was just an attempt out of sheer
desparation and I wanted to see if I can resolve cnames.
I have now created a ne A-record, named it "mail" and gave it the same
IP adresse (so I have two A-records for 192.168.2.1). I then created
an MX record and pointed it to that newly created A-record named
"mail". NOw I can resolve mail.sven.b, but it is only resolving the A-
record.
I then did an nslookup, set type=mx and search for "sven.b". This
returned no MX record.
Maybe I should add that the SOA is dc.sven.b and it is an AD
integrated DNS.
I'm still scratching my head....
|
|
svenberger1972[ at ]googlemail.com wrote:
[Quoted Text] >> An MX record has to specify an A record (not an IP address, not a
>> CNAME, etc). You need to create an A record for mail.sven.b and then
>> set that as the MX record for sven.b.- Hide quoted text -
>>
>> - Show quoted text -
>
> HI Lanwench,
>
> thanks for picking up the baton.
>
> I thought I did have an A-record in the DC (dc A
> 192.168.2.1 )
Not just *an* A record. Whatever you're going to use for an MX record must
exist as an A record.
> and used that to have the MX record pointed to (mail
> MX [10] dc.sven.b). The cname was just an attempt out of sheer
> desparation and I wanted to see if I can resolve cnames.
Sure.
>
> I have now created a ne A-record, named it "mail" and gave it the same
> IP adresse (so I have two A-records for 192.168.2.1).
That's fine. You can have pretty much as many as you wish.
> I then created
> an MX record and pointed it to that newly created A-record named
> "mail". NOw I can resolve mail.sven.b, but it is only resolving the A-
> record.
>
> I then did an nslookup, set type=mx and search for "sven.b". This
> returned no MX record.
Did you clear your cache?
>
> Maybe I should add that the SOA is dc.sven.b and it is an AD
> integrated DNS.
>
> I'm still scratching my head....
I'm not a DNS guru at all, but what you describe sounds right. You might
want to compose a new post, with the updated information, and post a new
message in here to see if you get new "eyes" on the post.
|
|
In news:54fd4148-0a25-41ff-b3b0-9f1ca2091f64[ at ]z6g2000pre.googlegroups.com,
svenberger1972[ at ]googlemail.com <svenberger1972[ at ]googlemail.com> requesting
assistance, typed the following:
[Quoted Text] >> An MX record has to specify an A record (not an IP address, not a
>> CNAME, etc). You need to create an A record for mail.sven.b and then
>> set that as the MX record for sven.b.- Hide quoted text -
>>
>> - Show quoted text -
>
> HI Lanwench,
>
> thanks for picking up the baton.
>
> I thought I did have an A-record in the DC (dc A
> 192.168.2.1 ) and used that to have the MX record pointed to (mail
> MX [10] dc.sven.b). The cname was just an attempt out of sheer
> desparation and I wanted to see if I can resolve cnames.
>
> I have now created a ne A-record, named it "mail" and gave it the same
> IP adresse (so I have two A-records for 192.168.2.1). I then created
> an MX record and pointed it to that newly created A-record named
> "mail". NOw I can resolve mail.sven.b, but it is only resolving the A-
> record.
>
> I then did an nslookup, set type=mx and search for "sven.b". This
> returned no MX record.
>
> Maybe I should add that the SOA is dc.sven.b and it is an AD
> integrated DNS.
>
> I'm still scratching my head....
Sorry for reading this so late. For MX records, you create them WITHOUT a
hostname. Create the hostname first and provide an IP, then create the MX
record pointing to the hostname without providing a hostname. This is based
on the RFC rules for MX records. Otherwise the resolution attempt may loop
and not get anything out of it at all.
To resolve an MX record, use nslookup:
nslookup
> set q=MX
sven.b
(your results will display here)
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT
Microsoft Certified Trainer
For urgent issues, you may want to contact Microsoft PSS directly.
Please check http://support.microsoft.com for regional support phone
numbers.
|
|
|