From: Paul English <tallpaul@speakeasy.org>
To: lartc@vger.kernel.org
Subject: [LARTC] equalize and DNS zone transfers
Date: Thu, 06 Jun 2002 19:14:48 +0000 [thread overview]
Message-ID: <marc-lartc-102339088408741@msgid-missing> (raw)
Hi everyone,
I'm new to the list and I've got a couple of questions. I'm
following instructions here:
http://www.samag.com/documents/s\x1824/sam0201h/0201h.htm
for setting up a dual-connection (T1 & DSL) machine. My problems are:
1) ip route add default equalize doesn't work - I get:
>ip route add default equalize
RTNETLINK answers: No such device
or if I do it properly:
>ip route add default equalize nexthop via 206.253.195.209 dev eth0
nexthop via 64.133.254.73 dev eth2
RTNETLINK answers: Invalid argument
2) Since that didn't work, I just made my default be via 64.133.254.73.
Now I'm running a DNS master server on 206.253.195.209 and while it
responds to regular dig just fine, it doesn't respond to zone transfer
(dig axfr ). Or rather, I've been told by the guy running the slave server
that for whatever reason it responds over the 64.133.254.73 address,
although I'm not sure how he found that out - so zone transfers don't
work.
I'm aware that #2 _could_ be due to my ipchains configuration being
incorrect, but I have poked some pretty big holes for the slave servers.
3) I see Policy Routing Using Linux by Matthew Marsh highly recommended on
this site: http://defiant.coinet.com/iproute2/
Are there any books that people would recommend even more highly? I'm
finding the command-reference only documentation on the net to be a bit
less than I need.
Thanks,
Paul
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2002-06-06 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 19:14 Paul English [this message]
2002-06-06 19:27 ` [LARTC] equalize and DNS zone transfers William L. Thomson Jr.
2002-06-06 19:46 ` William L. Thomson Jr.
2002-06-10 23:43 ` Paul English
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-102339088408741@msgid-missing \
--to=tallpaul@speakeasy.org \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.