Am 30.04.2015 um 12:55 schrieb Matus UHLAR - fantomas:
On 4/30/15, 12:16 AM, "Tom Robinson" <tom.robin...@motec.com.au> wrote:BTW, where can I see the results of my configuration changes? It would be nice to confirm that my changes have rectified the situation.On 30.04.15 01:38, Dave Pooser wrote:On the server (via SSH or console) use the +trace argument to dig, and then look for lines starting with ';;': postmstr@smtp:~$ dig +trace example.com.multi.uribl.com | grep ';;' ;; global options: +cmd ;; Received 913 bytes from 127.0.0.1#53(127.0.0.1) in 8 ms ;; Received 760 bytes from 199.7.91.13#53(d.root-servers.net) in 48 ms ;; Received 707 bytes from 192.54.112.30#53(h.gtld-servers.net) in 124 ms ;; Received 553 bytes from 54.149.125.143#53(o.icudp.com) in 74 ms ;; Received 206 bytes from 52.68.34.21#53(gg.uribl.com) in 147 ms So you can see that my mail server is querying its local DNS resolver, which is querying the root servers and then working its way down to the appropriate uribl.com server. In your case your actual IPs will be different, but the pattern should still hold.no, it's the "dig" command that does the trace, not the nameserver. This says nothing about your nameserver configuration, and it can't since nameserver does not provide that info
correct because the nameserver of the machine below *for sure* does not recursion but is a forwarder to a local cache which don't appear
[harry@srv-rhsoft:~]$ dig +trace example.com.multi.uribl.com | grep ';;' ;; global options: +cmd ;; Received 239 bytes from 127.0.0.1#53(127.0.0.1) in 0 ms ;; Received 751 bytes from 202.12.27.33#53(m.root-servers.net) in 43 ms ;; Received 698 bytes from 192.41.162.30#53(l.gtld-servers.net) in 186 ms ;; Received 544 bytes from 94.228.131.217#53(p.icudp.net) in 32 ms ;; Received 90 bytes from 184.73.199.129#53(ee.uribl.com) in 173 ms
signature.asc
Description: OpenPGP digital signature
