Main Topics
Browse All TopicsHi guys - what do I put into /etc/named.conf so that this...
dig -x 192.168.0.123
works, and also,
dig 192-168-0-123.mylan.com
works
preferably also this working too:-
dig 192-168-0-123.mylan.com mx
I want it to resolve all 256 IP addresses from 192.168.0.0 through 192.168.0.255
Thanks for your help!!!
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.
Here's part of what I think I need - but note the '-*' does not work
1 PTR 172-22-0-1.mylan.com.
* PTR 172-22-0-*.mylan.com.
7 PTR 172-22-0-77.mylan.com.
# dig @127.0.0.1 -x 172.22.0.2
;; ANSWER SECTION:
2.0.22.172.in-addr.arpa. 86400 IN PTR 172-22-0-*.mylan.com.
--------------------------
How do I fix this......................
Yeah - I know I could shove 256 entries in my HOSTS file and be done with it - but I'm trying to set up "bind" properly instead.
I doubt individual entries is the correct solution - especially since I already guessed that "*" works at the front of the line - surely there's a way to insert the "*" matched value as a variable in what gets returned; from just one config line?
Quote from http://www.ripe.net/ripe/m
"Wildcards" nowadays will produce sort of allergic reaction all over the place.
While you can of course apply them to PTR RRs in IN-ADDR.ARPA zones, they're
likely to break consistency. In addition, in a namespace as structured as
IN-ADDR.ARPA what's the advantage of '*' over some lines of perl script
(or BIND's $GENERATE) and "doing it right"?
BIND itself has a function to generate these entries - "$GENERATE".
You should read this howto on BINDs $GENERATE function, I think it's more like what you're looking for:
http://www.tech-recipes.co
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I will leave the following recommendation for this question in the Cleanup topic area:
Split: harbor235 & kamermans
Any objections should be posted here in the next 4 days. After that time, the question will be closed.
Cyclops3590
EE Cleanup Volunteer
Business Accounts
Answer for Membership
by: harbor235Posted on 2005-10-26 at 04:54:17ID: 15161536
http://www.tldp.org/HOWTO/ DNS-HOWTO- 3.html#cac hing
king.com/l inux-hn/dn s- static.h tm#_Toc928 08687
http://www.linuxhomenetwor
harbor235 ;}