/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting!
/* ALSO: Don't quote this header. It makes you look lame :-) */
Brian Dube wrote:
> I can't pinpoint the cause of this problem so it may not be a masquerading
> issue.. however, I've never had this problem before masquerading. Lately
> the firewall/masq machine is trying to resolve everything as belonging to
> itself. For example, trying to ping/telnet to somedomain.com, the name and
> address for somedomain.com.mydomain.com is returned. Which happens to work
> because my DNS services provide a wildcard entry to resolve *.mydomain.com
> to my IP address, but the result in this case is certainly not what I
> wanted. I've never had this happen before and I can't figure out why it
> started doing this. If anyone has had this problem or knows the cause, I'd
> love to get it fixed.
it doesn't have anything to do with masquerading. it sounds
like a combination of the default search list in your
/etc/resolv.conf (search mydomain.com) and the wildcard dns
entry. maybe you should only use wildcards for mx records?
i'm not sure, never used them.
either that or you should probably be using that name server
with the wildcard for external queries and a separate name
server without the wildcard for internal queries.
you could change your search list to nothing by removing any
"domain" and "search" lines but that's very drastic. local
names wouldn't resolve.
you can suppress the behaviour in the meantime by
always putting a "." at the end of every external
hostname (e.g. "somedomain.com.") which bypasses
the search list.
raf
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
Admin requests can be handled at http://www.indyramp.com/masq-list/ --
THIS INCLUDES UNSUBSCRIBING!
or email to [EMAIL PROTECTED]
PLEASE read the HOWTO and search the archives before posting.
You can start your search at http://www.indyramp.com/masq/
Please keep general linux/unix/pc/internet questions off the list.
