Error 400 when using DynDNS domain name with Underscore.



  • Had a strange one today, installed a customer firewall, Teamviewere'd into my server at home to check that I could login remotely, and was getting a 400 - Bad Request error.

    I had an underscore in the DynDNS domain name for the firewall and that was stopping it from working, interestingly enought, it was stopping OpenVPN from connecting too. Changed the unserscores to Hyphens and it works now.

    Running on an APU-1D Board -

    2.2.1-RELEASE (amd64)
    built on Fri Mar 13 08:16:49 CDT 2015
    FreeBSD 10.1-RELEASE-p6


  • Banned

    @The:

    Had a strange one today, installed a customer firewall

    2.2.1-RELEASE (amd64)
    built on Fri Mar 13 08:16:49 CDT 2015
    FreeBSD 10.1-RELEASE-p6

    Any good reason why you installed 2.2.1, beyond the fact that it has tons of unfixed bugs, incl. serious issues with filesystem corruption?



  • @The:

    Had a strange one today, installed a customer firewall, Teamviewere'd into my server at home to check that I could login remotely, and was getting a 400 - Bad Request error.

    I had an underscore in the DynDNS domain name for the firewall and that was stopping it from working, interestingly enought, it was stopping OpenVPN from connecting too. Changed the unserscores to Hyphens and it works now.

    Running on an APU-1D Board -

    2.2.1-RELEASE (amd64)
    built on Fri Mar 13 08:16:49 CDT 2015
    FreeBSD 10.1-RELEASE-p6

    Was the underscore in the primary domain name or in a subdomain?

    Ex: _here.example.com or example.he_re.com?



  • @doktornotor:

    Any good reason why you installed 2.2.1, beyond the fact that it has tons of unfixed bugs, incl. serious issues with filesystem corruption?

    No, I need to go and update the firmware, changing from SD cards to mSATA so they'll play nice with the latest builds.

    @Trel:

    Was the underscore in the primary domain name or in a subdomain?

    Ex: _here.example.com or example.he_re.com?

    In the subdomain, it was -

    xxx_1cr_1.mydomain.xxx

    changed to

    xxx-1cr-1.mydomain.xxx and it's fine now.


  • LAYER 8 Global Moderator

    Quick google shows that yeah _ not valid in fqdn

    https://en.wikipedia.org/wiki/Hostname#Restrictions_on_valid_host_names

    So webserver should balk at you with a 400 that its malformed..



  • There we go, something learnt every day and all that :) Cheers.


Log in to reply