The mixing CNAME and others (SOA, NS) is used around. The question is how to make pdnsd to handle it. As You can see pdnsd can handle adaptec.com case, yet it fails on rdir.pl ?
Main Topics
Browse All TopicsI'm using the pdnsd-1.2.7-par happily as my dns server, but it seem I cannot solve one problem, maybe someone could help?
there's domain rdir.pl
I cannot resolve A for that very name.
I can do it by hand
[root@firebrick etc]# host -t ns rdir.pl
rdir.pl name server dns2.home.pl.
rdir.pl name server dns3.home.pl.
rdir.pl name server dns.home.pl.
[root@firebrick etc]# host -t cname rdir.pl dns.home.pl
Using domain server:
Name: dns.home.pl
Address: 62.129.252.30#53
rdir.pl is an alias for beta.blip.pl.
[root@firebrick etc]# host beta.blip.pl
beta.blip.pl has address 91.197.13.171
beta.blip.pl has address 91.197.13.170
but querying pdnsd
[root@firebrick etc]# host rdir.pl localhost
Host rdir.pl not found: 2(SERVFAIL)
The ANY query returns
[root@firebrick etc]# host -a rdir.pl localhost
Trying "rdir.pl"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19968
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 3
;; QUESTION SECTION:
;rdir.pl. IN ANY
;; ANSWER SECTION:
rdir.pl. 86400 IN NS dns2.home.pl.
rdir.pl. 86400 IN NS dns3.home.pl.
rdir.pl. 86400 IN NS dns.home.pl.
rdir.pl. 85665 IN SOA dns.home.pl. admin.home.pl. 1209996961 10800 3600 604800 3600
;; ADDITIONAL SECTION:
dns2.home.pl. 3500 IN A 213.25.47.166
dns3.home.pl. 3503 IN A 216.93.176.64
dns.home.pl. 3493 IN A 62.129.252.30
obviously there's no CNAME (mixing cname and others records is not allowed, right?).
Strangely, it seems that other similar configurations are handled fine, example is adaptec.com
My pdnsd config is
global {
perm_cache=16384;
cache_dir="/var/cache/pdns
pid_file = /var/run/pdnsd.pid;
run_as="pdnsd";
strict_setuid = on;
tcp_server = on;
server_port = 53;
server_ip = 0.0.0.0;
status_ctl = off;
paranoid=off;
query_method=udp_tcp;
min_ttl=10m;
max_ttl=1d;
neg_ttl=5m;
timeout=10;
}
server {
label= "myisp";
proxy_only = off;
root_server=on;
ip = 198.41.0.4, 192.228.79.201, 192.33.4.12, 128.8.10.90, 192.203.230.10, 192.5.5.241, 192.112.36.4, 128.63.2.53, 192.36.148.17, 192.58.128.30, 193.0.14.129, 199.7.83.42, 202.12.27.33;
randomize_servers = on;
caching = on;
lean_query = off;
timeout=10;
uptest=query;
interval=15m;
purge_cache=off;
}
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Adaptec.com bind two A records to the zone name, no CNAMEs, it doesn't compare well.
The MX record for rdir.pl fails to resolve as well due to it being mixed with the CNAME. While NS records with CNAMEs may be implemented in some cases, mixing MX records is not, neither conform to RFC 1035.
Going to bow-out of this one. I read your original question as a request for help with the zone file (which I can do) rather than a request to modify the behaviour / code of PDNSD (which I cannot do).
Hopefully someone else will be able to help you out.
Chris
Appeared that for both, rdir.pl and www.adaptec.com theirs dns servers are somehow buggy(rfc incompatible).
I got really fast support from http://www.phys.uu.nl/~rom
Business Accounts
Answer for Membership
by: Chris-DentPosted on 2008-12-18 at 05:41:54ID: 23203162
There does seem to be a CNAME here:
rdir.pl. 3600 IN CNAME beta.blip.pl.
;; Received 49 bytes from 62.129.252.30#53(dns.home.
And you're right about the limitation on CNAMEs it cannot be used for the domain name itself, rdir.pl already has SOA and NS records bound to it.
Chris