about DNAME question

[MontyRee]

CkhlbGxvLCBhbGwuCiAKVGhhbmtzIGZvciBraW5kIGFuc3dlcmluZyBmb3IgRE5BTUUuCkkgaGF2
ZSBhZGRpdGlvbmFsIHF1ZXN0aW9ucyBmb3IgRE5BTUUuCiAKSWYgSSBzZXQgbGlrZSBiZWxvdywg
CiAKZXhhbXBsZS5jb20uICAgICAgICAgICAgICBJTiBETkFNRSAgICAgICAgZXhhbXBsZTIuY29t
CgpJUCBhZGRyZWVzcyBvZiBleGFtcGxlLmNvbSBpcyAxOTIuMTY4LjEuMiAKIAogCjEuIGlmIGNs
aWVudCByZXNvbHZlciB1c2UgYmluZCA4IG9yIGJlbG93IG9sZCB2ZXJzaW9uLgogICBXaGF0IHdv
dWxkIGJlIGhhcHBlbj8KICAgQ2FuIHJlY29nbml6ZSBETkFNRSByZWNvcmQgd2VsbD8KIAogCjIu
IGlmIEkgcXVlcnkgZXhhbXBsZS5jb20sIGl0IHJldHVybnMgTlhET01BSU4gaW5zdGVhZCBvZiAx
OTIuMTY4LjEuMi4KICAgSG93IHRvIHNvbHZlIHRoaXMgcHJvYmxlbT8KIAogCgpUaGFua3MgaW4g
YWR2YW5jZS4KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18Ku/W3zr/2wfggx9a43sDPISC5q7fhIFBPUDO3ziDFuLjewM8sIMWs
tvPAzL7wxq4gv6y1v7W1IMDawK+307DUIQpodHRwOi8vbWFpbC5saXZlLmNvbQpfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpiaW5kLXVzZXJzIG1haWxpbmcg
bGlzdApiaW5kLXVzZXJzQGxpc3RzLmlzYy5vcmcKaHR0cHM6Ly9saXN0cy5pc2Mub3JnL21haWxt
YW4vbGlzdGluZm8vYmluZC11c2Vycw==

[Barry Margolin]

What's worse than a mail-to-news gateway that leaving the multipart crap
headers in the body but removing the "Content-Type:
multipart/alternative" line from the header....

In article <gt61o2$2t66$1...@sf1.isc.org>, MontyRee <chul...@hotmail.com>
wrote:

--
Barry Margolin, bar...@alum.mit.edu
Arlington, MA
*** PLEASE don't copy me on replies, I'll read them in the group ***
_______________________________________________
bind-users mailing list
bind-...@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

[Niall O'Reilly]

On Tue, 2009-04-28 at 04:46 +0000, MontyRee wrote:
> If I set like below,
>
> example.com. IN DNAME example2.com
>
> IP addreess of example.com is 192.168.1.2
>
>
> 1. if client resolver use bind 8 or below old version.
> What would be happen?
> Can recognize DNAME record well?
>
>
> 2. if I query example.com, it returns NXDOMAIN instead of 192.168.1.2.
> How to solve this problem?

You need to keep in mind that DNAME provides 'aliasing'
for domain names _below_ the name to which the DNAME belongs,
and _not_ for the name itself.

The DNAME record you've shown provides a hierarchy of mappings,
including the following:

a.example.com. -> a.example2.com.
tasty.example.com. -> tasty.example2.com.
sandwich.example.com. -> sandwich.example2.com.
is.what.i.want.for.lunch.example.com. ->
is.what.i.want.for.lunch.example2.com.

It doesn't do anything for example.com. itself.
You'll need to add A, AAAA, MX, records as needed.

/Niall