AWS EC2 DNS issue

Discussion in 'ISPConfig 3 Priority Support' started by Ark74, Oct 21, 2017.

  1. Ark74

    Ark74 Member

    Recently I'm finding some issues with DNS and AWS.
    At the beginning when I changed the domain name and set the glue records and dns settings I was able to create A records, MX records, TXT records, etc.
    But now I find very weird that any attempt to create any other new record is not taken into account.
    Bind seem to work properly (otherwise) DNS would not work but DNS propagation for new records don't.

    This is a first with EC2, I'm using another hosting companies for over a year now with no issues.

    Is there a knowledge base with issues on AWS?
    Have you experienced this before?
    Any suggestion that I should take into account?

    Thanks in advance.
  2. Ark74

    Ark74 Member

    On a closer look, new changes are not been recorded.

    $ dig @ A

    ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @ A
    ; (1 server found)
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 25520
    ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
    ;; WARNING: recursion requested but not available

    ; EDNS: version: 0, flags:; udp: 4096
    ; IN A

    ;; AUTHORITY SECTION: 3600 IN SOA 2017101904 7200 540 604800 3600

    ;; Query time: 95 msec
    ;; SERVER:
    ;; WHEN: Sat Oct 21 11:19:23 CDT 2017
    ;; MSG SIZE rcvd: 108​

    So my guess is it's a local issue.
  3. Ark74

    Ark74 Member

    Sorry guys! I found the issue.
    I had a bad record that's the reason the changes weren't been applied. They remained as a .err file.

    Now it's working fine. Thanks!
    till and ahrasis like this.

Share This Page