Join the Conversation

To sign in, use your existing MySonicWall account. To create a free MySonicWall account click "Register".

Does anyone else have also massive problems to send emails ?

2»

Answers

  • BWCBWC Cybersecurity Overlord ✭✭✭

    Sorry for the double post.

    I'am confused, did SNWL really revert back to the DNS misconfiguration and everything will start all over again? BTW, same goes again for snwlhosted.com

    @David W any take on that?


    % dig @8.8.8.8 NS snwlhostedeu.com                      
    
    ; <<>> DiG 9.10.6 <<>> @8.8.8.8 NS snwlhostedeu.com
    ; (1 server found)
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27006
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 512
    ;; QUESTION SECTION:
    ;snwlhostedeu.com.       IN   NS
    
    ;; ANSWER SECTION:
    snwlhostedeu.com.    1268  IN   NS   sjl0vm-heswd01.colo.sonicwall.com.
    snwlhostedeu.com.    1268  IN   NS   ns2.snwlhostedeu.com.
    snwlhostedeu.com.    1268  IN   NS   ns1.snwlhostedeu.com.
    
    ;; Query time: 22 msec
    ;; SERVER: 8.8.8.8#53(8.8.8.8)
    ;; WHEN: Sat Apr 17 09:43:52 CEST 2021
    ;; MSG SIZE rcvd: 125
    
    
    
    % dig @8.8.8.8 A sjl0vm-heswd01.colo.sonicwall.com
    
    ; <<>> DiG 9.10.6 <<>> @8.8.8.8 A sjl0vm-heswd01.colo.sonicwall.com
    ; (1 server found)
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 15465
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 512
    ;; QUESTION SECTION:
    ;sjl0vm-heswd01.colo.sonicwall.com. IN A
    
    ;; AUTHORITY SECTION:
    sonicwall.com.     299   IN   SOA   pdns1.ultradns.net. hostmaster.sonicwall.com. 2017093180 1200 180 604800 300
    
    ;; Query time: 33 msec
    ;; SERVER: 8.8.8.8#53(8.8.8.8)
    ;; WHEN: Sat Apr 17 09:44:07 CEST 2021
    ;; MSG SIZE rcvd: 127
    

    --Michael@BWC

  • David WDavid W SonicWall Employee

    @BWC no, at least it wasn't done on purpose.

    I've informed the back end again about it.

    David Wilbur

     Technical Support Senior Advisor, Premier Services , SME Email Security

  • BWCBWC Cybersecurity Overlord ✭✭✭
    edited April 17

    @David W it's back to "normal" again, but it's still badly configured.

    Your authoritative DNS is returning this, having both NS pointing to the same IP address is bad design and asks for a single point of failure. You should check your glue records for that. At least the non-resolving entry is removed again.

    snwlhostedeu.com.    1799  IN   NS   ns1.snwlhostedeu.com.
    snwlhostedeu.com.    1799  IN   NS   ns2.snwlhostedeu.com.
    
    ns1.snwlhostedeu.com.   1785    IN      A       173.240.221.20
    ns2.snwlhostedeu.com.   1799    IN      A       173.240.221.20
    

    This is what the TLD NS returns, why not stick with that?

    # dig @a.gtld-servers.net NS snwlhostedeu.com
    
    
    ; <<>> DiG 9.16.1-Ubuntu <<>> @a.gtld-servers.net NS snwlhostedeu.com
    ; (2 servers found)
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53731
    ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 3
    ;; WARNING: recursion requested but not available
    
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;snwlhostedeu.com.              IN      NS
    
    
    ;; AUTHORITY SECTION:
    snwlhostedeu.com.       172800  IN      NS      ns1.snwlhostedeu.com.
    snwlhostedeu.com.       172800  IN      NS      ns2.snwlhostedeu.com.
    
    
    ;; ADDITIONAL SECTION:
    ns1.snwlhostedeu.com.   172800  IN      A       173.240.221.20
    ns2.snwlhostedeu.com.   172800  IN      A       173.240.209.20
    
    
    ;; Query time: 24 msec
    ;; SERVER: 192.5.6.30#53(192.5.6.30)
    ;; WHEN: Sat Apr 17 19:35:59 CEST 2021
    ;; MSG SIZE  rcvd: 113
    

    --Michael@BWC

  • ThKThK Enthusiast ✭✭

    @BWC one customer didn´t receive email after 7 am. About 10 am emails getting in , a few. Now it seems it doesn´t work again. but what if it is only so slow ...

    sending out is quiet realtime...

    On MXtoolbox the DNS now shows : again both on 173.240.221.20


  • BWCBWC Cybersecurity Overlord ✭✭✭

    Hi @ThK ... I checked and did not see any new bounces, the SNWL DNS is just poorly configured but does not do any harm at the moment, IMHO.

    --Michael@BWC

Sign In or Register to comment.