How create a wildcard record on ISP DNS module?

Discussion in 'General' started by dioobr, Jun 16, 2016.

  1. dioobr

    dioobr New Member

    Hello,

    When I try to create a new DNS TXT record on IPSConfig 3.0.5, return this error: "The hostname has the wrong format."
    Here what I fill:
    Hostname: *.example.com
    Text: The hostname has the wrong format.
    TTL: 3600

    What's wrong?
     
  2. florian030

    florian030 ISPConfig Developer ISPConfig Developer

    Did you try "*.example.com." and also just "*" ?
     
  3. dioobr

    dioobr New Member

    Yepp... and show the same error message. I don't understand. I think I did it before, but now don't work.
     
  4. florian030

    florian030 ISPConfig Developer ISPConfig Developer

    I can create an A-Record
    *.example.com. IP 10.11.12.13 without any problems.
     
  5. dioobr

    dioobr New Member

    Here too, for A record, but not for TXT record. Try you.
     
  6. florian030

    florian030 ISPConfig Developer ISPConfig Developer

    sorry, i missed the txt-part. Why do you need a txt-record for a wildcard-host?
     
  7. Jesse Norell

    Jesse Norell Active Member

    One use case is SPF, eg. "v=spf1 -all" will help cut a small amount of spam. I've logged completely unrelated 3rd party mail servers delivering to other 3rd party servers but identifying as a hostname on our domain, and having such an SPF record allows/requests the latter to block it.
     
  8. dioobr

    dioobr New Member

    To provide SPF information, like Jesse said.
     
  9. florian030

    florian030 ISPConfig Developer ISPConfig Developer

    Create one SPF-Record for each domain. There is no need for a wildcard for a SPF-Record (at least i don't know any reason)
     
  10. dioobr

    dioobr New Member

    Are 130 subdomains, when it could be just an SPF record. Could be part of a future update, what do you think?
     
  11. florian030

    florian030 ISPConfig Developer ISPConfig Developer

    You can change the code to fit your needs. I see no reasons for 130 subdomains.
     

Share This Page