dns – Determining DKIM Selector and Key Values for my domain, hosted on 1&1

I have a client that is with 1&1 (yeah, I know). He’s asked me to set up SPF and DKIM records for his domain.

I am not experienced with email configuration (I’m just a lowly web developer) but I managed to figure out the correct settings for the SPF record (using TXT type) but I just cannot figure out what to do about the DKIM. I know it needs the type to be TXT but I have no idea what the prefix selector should be and no idea what the value should be either. In the examples I’ve found the value is a long string of characters…and thats about the extent of my knowledge.

Any pointers would be gratefully received.

EDIT 1: More Info
Turns out 1&1 only support DKIM on dedicated hosting accounts, not shared hosting as my client is on. Oh well.

Multisite – How to get blog posts from main domain and show in all other subdomin

I have created multisite network and I want to get some ( 3-4 ) blog post from main site and want to show in child websites in home page with the help of shortcode. I am using the same theme to all websites (main and child). I am working on this from last two days but I have not get any idea. Can you please guide me on this.


Would a two word domain name with a shared letter between the words be treated the same for SEO as the fuller name?

I found a domain name (2 words) that is not available. Then I found almost the same domain name with a slight difference, the last letter of the first word is the same of the first letter of the second word.

Ex : jamessecret.com (not available)
     jamesecret.com (available)

In terms of SEO, is it seen as the same to Google? Would search engines interpret them the same?

seo – Partial domain names

i have a question regarding domain names, i found a domain name (2 words) that is not available, but than i found almost the same domain name with a slight difference, the last leter of the first word is the same of the first letter of the second word.

Ex : jamessecret.com (not available)
    jamesecret,com (available)

In terms of seo, is it seed has the same to google, does search engine interprets the same?

If I have 2 services sending email using my domain name, can I set up DKIM for one but not the other?

I develop WordPress websites and frequently create contact forms that send email with a From address using the domain name of the website. Typically the business that the website is for is already using their own email service, which may or may not be configured with DKIM.

Whether or not DKIM is already set up for the existing email service (let’s say it’s Office365) using the domain, I want to know whether I can negatively affect the deliverability of the email from the existing email service if I add a DKIM key for an additional mail server (used by the WordPress website) to send email, with a From address containing the domain name.

ie assuming I configure a DKIM record correctly for the WordPress website to send email using the mail server of the hosting service, can the Office365 email deliverability be affected?

Note: I do see it’s possible to have 2 DKIM records, for multiple services, but they must have different selectors: https://stackoverflow.com/questions/32649006/can-i-have-multiple-dkim-txt-records-in-single-domain

dns – How can a domain be showing as pendingDelete & redemptionPeriod, but not expire for another year?

This is absolutely normal, at least for a gTLD (you didn’t even mention the TLD…)

The expiration date was 2020-06-18. At this time the registry auto renewed the domain, which means if you look at the registry whois or RDAP server you will now see an expiration date of 2021-06-18. If you look at the registrar whois or RDAP server you would see that its own expiration date has not changed (this is one of the hidden corner of the current domain name lifecycle, I tried to explain that more in details at https://serverfault.com/a/885149/396475).

But this means that after this date, the expiration will now always be seen as 2021-06-18 until the domain is either finally deleted (after redemptionPeriod and pendingDelete grace periods), or really renewed.

Starting at this time, the registrar has 45 days to delete the domain, after that the domain is definitively renewed. If the domain is deleted during those 45 days, then the registrar is not billed (or refunded if billed already) for the auto-renewwal.

Hence 2020-06-18 + 45 days = 2020-08-02.

Based on your output, right before that date, on 2020-07-30 an update happened.
I guess, at that point, the registrar decided to delete the domain name.

When that happen the domain is placed on redemptionPeriod which means that the registrar has some time to “undelete” it, in case of errors. Which is why the second status is pendingDelete. It is only some time after (depending on registry policies), that the domain switches to a state where the registrar can not restore it anymore. You will then see pendingDelete twice in whois output, and no redemptionPeriod.

In gTLD, the “redemption period” is typically 30 days. So you may expect at 2020-07-30 + 30 days = 2020-08-29 to see a change in status (if the registrar does not restore it before that date),
and then as the final pendingDelete period is typically 5 days, around 2020-09-03 the domain would be definitively deleted.

This is explained in the RFC about redemption, RFC 3915.
See this text and state diagram:

2.  Redemption Grace Period State Diagram

   The Redemption Grace Period (RGP) involves several domain state
   transitions as a domain name moves through the redemption process:

   1.  A domain is initially in the EPP "ok" status, or some other
       status that allows processing of the EPP <delete> command.

   2.  A <delete> command is received and processed for the domain name.

   3.  RGP begins once the <delete> command is processed successfully.
       The EPP status changes to "pendingDelete", and the RGP status is
       initialized to "redemptionPeriod".  The domain remains in this
       state until either a <restore> operation is requested or the
       redemption period elapses.

   4.  A <restore> operation can be requested using the extended EPP
       <update> command.  Go to step 8 if the redemption period elapses
       before a <restore> request is received.

   5.  If the <restore> is successful, the Registry waits to receive a
       restore report from the registrar for a period of time defined by
       the Registry.  The EPP status remains "pendingDelete" and the RGP
       status changes to "pendingRestore".  While this extension defines
       a method to deliver a restore report via EPP, an out-of-band
       mechanism (such as a web site) can also be used to deliver
       restore reports.

   6.  The domain name returns to the redemption period state (state 3)
       if a restore report is not received.

   7.  If a restore report is received the EPP status returns to "ok"
       (or whatever it was prior to processing the <delete> command),
       and the RGP status is removed completely.

   8.  The redemption period elapses before a <restore> request is

   9.  The EPP status remains "pendingDelete" and the RGP status changes
       to "pendingDelete".  The domain name remains in this state for a
       period of time defined by the Registry.

   10. The domain name is purged once the pending delete period elapses.

   11. The domain name is available for re-registration.

   Figure 1: RGP State Diagram

   +----------------------+    (2)   +----------------------+
   |EPP: ok            (1)| <delete> |EPP: pendingDelete (3)|
   |RGP: N/A              |--------->|RGP: redemptionPeriod |
   +----------------------+          +----------------------+
      ^                         (4)    |  ^             |
      |                      <restore> |  |      No (8) |
      |                    +-----------+  |   <restore> |
      |                    |              |             |
      |                    v              |             v
      |  +----------------------+         |  +----------------------+
      |  |EPP: pendingDelete (5)|         |  |EPP: pendingDelete (9)|
      |  |RGP: pendingRestore   |---------+  |RGP: pendingDelete    |
      |  +----------------------+ Report     +----------------------+
      |                    |      not (6)               |
      |          (7)       |      Received   Purge (10) |
      |    Report Received |                            |
      +--------------------+                            v
                                             |       Purged     (11)|
                                             |                      |

(the fact that you have two EPP statuses is indeed hugely confusing, specially when both are “pendingDelete”; this comes from the fact that all of this is called the “rgp” EPP extension, it was not designed in core EPP but added later, so to fit it in the framework it has to create new statuses that way).

You can also look at ICANN timeline:
enter image description here

and ICANN explanations on EPP status (the whois output shows the links):

https://icann.org/epp#redemptionPeriod :

This status code indicates that your registrar has asked the registry to delete your domain. Your domain will be held in this status for 30 days. After five calendar days following the end of the redemptionPeriod, your domain is purged from the registry database and becomes available for registration.

https://icann.org/epp#pendingDelete :

This status code may be mixed with redemptionPeriod or pendingRestore. In such case, depending on the status (i.e. redemptionPeriod or pendingRestore) set in the domain name, the corresponding description presented above applies. If this status is not combined with the redemptionPeriod or pendingRestore status, the pendingDelete status code indicates that your domain has been in redemptionPeriod status for 30 days and you have not restored it within that 30-day period. Your domain will remain in this status for several days, after which time your domain will be purged and dropped from the registry database.

Once deletion occurs, the domain is available for re-registration in accordance with the registry’s policies.

findinstance – Why does specifying the solution domain seriously affect the solution speed?

I want to solve the problem of this post. After trying, I found a strange problem.

When I specify the solution field as a real field, the code runs all the time:

Q = {{x1, x2, 1/Sqrt(2)}, {x3, x4, 0}, {x5, x6, 1/Sqrt(2)}}; 
A = Array(x, {3, 3}); 
 Transpose(Q) . A . Q == {{1, 0, 0}, {0, 1, 0}, {0, 0, 0}} && 
     Transpose(Q) . Q == IdentityMatrix(3), 
 Join({x1, x2, x3, x4, x5, x6}, 
     Flatten(A)), Reals)

When I remove the Reals option, I can get the results quickly, although the results are still real numbers:

Q = {{x1, x2, 1/Sqrt(2)}, {x3, x4, 0}, {x5, x6, 1/Sqrt(2)}}; 
A = Array(x, {3, 3}); 
 Transpose(Q) . A . Q == {{1, 0, 0}, {0, 1, 0}, {0, 0, 0}} && 
     Transpose(Q) . Q == IdentityMatrix(3), 
 Join({x1, x2, x3, x4, x5, x6}, 

(*{{x1 -> 0, x2 -> -(1/Sqrt(2)), x3 -> -1, x4 -> 0, x5 -> 0, 
     x6 -> 1/Sqrt(2), x(1, 1) -> 1/2, x(1, 2) -> 0, 
     x(1, 3) -> -(1/2), x(2, 1) -> 0, x(2, 2) -> 1, 
     x(2, 3) -> 0, x(3, 1) -> -(1/2), x(3, 2) -> 0, 
     x(3, 3) -> 1/2}}*)

I want to know why the Reals option seriously affects the speed of solution.

Domain Driven Design – where should I put this kind of struct?

for example:

type AParams struct {
   a int
   b string
   c ()anotherStruct
type ARepo interface {
    GetA(params Aparams, ...) (entity.A, error)
/// infra/repo/a_repo.go
//the implementation of ARepo interface goes here

My question is which layer should I put AParams struct to? And what is it called in DDD? Thanks.

In my opinion, it can be in infra layer coz the domain layer can call it in A repository interface

Is that possible to upload backup of domain “a” to domain “b”?

Hello, i’ve backup of " a" domain and i need to upload it to new domain "b" . I just have the backup of domain a and the domain a is exp… | Read the rest of https://www.webhostingtalk.com/showthread.php?t=1818432&goto=newpost

email – SPF and DKIM for one domain on two servers

I followed this guide to setup SPF and DKIM for emails to be sent from a server for a domain. That server is the location of the actual email server for the domain.

I now want to setup another server to be able to send emails from the domain via PHP. Can anyone suggest how this is done? Is it the exact same steps?