On Wednesday 15 August 2012 02:16 PM, Simon Kelley wrote:
If your 192.168.2.1 is local nameserver only handling certain domains,
you can configure dnsmasq to use it as such with the
server=/example.com/192.168.2.1
style configuration on /etc/dnsmasq.conf.
If I have 2 name servers, should
On 16/08/12 08:59, Ritesh Raj Sarraf wrote:
On Wednesday 15 August 2012 02:16 PM, Simon Kelley wrote:
If your 192.168.2.1 is local nameserver only handling certain domains,
you can configure dnsmasq to use it as such with the
server=/example.com/192.168.2.1
style configuration on
Package: dnsmasq
Version: 2.62-3
Severity: important
Simon,
Looks like, since your last fix of dnsmasq's integration with systemd,
something has broken. I am not sure where is the problem (could be
resolvconf too), but as far as I can remember this problem seems to have
begun since your last
On Wednesday 15 August 2012 01:47 PM, Ritesh Raj Sarraf wrote:
Looks like, since your last fix of dnsmasq's integration with systemd,
something has broken. I am not sure where is the problem (could be
resolvconf too), but as far as I can remember this problem seems to have
begun since your
On 15/08/12 09:17, Ritesh Raj Sarraf wrote:
Package: dnsmasq
Version: 2.62-3
Severity: important
Simon,
Looks like, since your last fix of dnsmasq's integration with systemd,
something has broken. I am not sure where is the problem (could be
resolvconf too), but as far as I can remember
On Wednesday 15 August 2012 02:16 PM, Simon Kelley wrote:
What does dig @192.168.2.1 smtp.corp.corpdomain.com return?
Nothing. Because that is my ISP's nameserver which has no information
about my workplace's hosts.
Assuming it's NXDOMAIN, that's your problem, and it's not a new one, but
the
6 matches
Mail list logo
